programming4us
           
 
 
Applications Server

Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 12) - Planning Public Folder Access and Migration

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
12/26/2010 8:53:24 AM

7. Planning Public Folder Access and Migration

This section discusses the considerations for coexistence and migration of public folders in your Exchange Server 2003 environment.

7.1. Public Folder Access via OWA

Although public folder servers can be replicated to Exchange Server 2010 at the same time as the rest of the Exchange Server 2010 infrastructure is implemented, you should retain public folder replicas on Exchange Server 2003 until all mailboxes have been migrated to Exchange Server 2010. This is to allow for access to public folders via Exchange Server 2003 OWA as well as Exchange Server 2010 Outlook Web App. The behavior for accessing public folders via various combinations of mailbox and public folder server versions is outlined in Table 12.

Table 12. Accessing Public Folders via OWA
MAILBOX LOCATIONPF LOCATIONOWA ACCESS TO PF FROM EXCHANGE SERVER 2010 CAS?OWA ACCESS TO PF FROM EXCHANGE SERVER 2003 OWA?
Exchange Server 2003Exchange Server 2003YesYes
Exchange Server 2003Exchange Server 2010NoNo
Exchange Server 2010Exchange Server 2003Yes (redirected to Exchange Server 2003 OWA)N/A
Exchange Server 2010Exchange Server 2010YesN/A

7.2. Migrating Public Folders

As mentioned in the previous section, you should retain public folder content on Exchange Server 2003 servers until all mailboxes have been moved to Exchange Server 2010, to ensure access to the content by Exchange Server 2003 OWA users. To replicate public folder content to Exchange Server 2010, it is recommended that you use the AddReplicaToPFRecursive.ps1 Windows PowerShell script, located in the <Exchange_Installation_Path>\Scripts directory on the Exchange Server 2010 computer. After all mailboxes have been moved to Exchange Server 2010, the public folder replicas can be removed by using the RemoveReplicaFromPFRecursive.ps1 script.

Lessons Learned: Invalid Categories Set on Public Folder Items

Markus Bellmann

Senior Solutions Architect, Siemens, Germany

I recently worked with a client who was migrating from Exchange Server 2003 to Exchange Server 2010. They use public folders extensively; they have 200 GB of data in almost 18,000 folders, with a total item count of more than 2,000,000 items; one folder alone had more than 125,000 items in it, and there is a significant amount of data that is more than 5 years old. As cleaning up their public folder infrastructure would involve working with multiple business units and persuading them to archive, and the many discussions about what can or can't be archived, this would have taken a considerable amount of time and delayed the Exchange Server 2010 project significantly, so they opted to replicate all the data to Exchange Server 2010 and undertake a public folder cleanup as an ongoing project at a later date. However, when we began replicating the public folders from Exchange Server 2003, we discovered that a significant amount of the content would not replicate; the Exchange Server 2003 information store was sending out folder content backfill messages, but these messages were failing on the store driver on the Exchange Server 2010 Hub Transport server. The cause was invalid Outlook Categories being set on the items in public folders; Exchange Server 2010 (as well as Exchange Server 2007) performs a significant amount of property validation to keep bad data from getting into the public folder store, so data that is accepted by Exchange Server 2003 is rejected by Exchange Server 2010. The invalid categories issue in particular is indicated by the following event logged on the Hub Transport Server:

Log Name:      Application
Source: MSExchange Store Driver
Event ID: 1020
Task Category: MSExchangeStoreDriver
Level: Error
Keywords: Classic
User: N/A
Description:
The store driver couldn't deliver the public folder replication message
"Folder Content Backfill Response" because the following error occurred:
Property validation failed. Property = [{00020329-0000-0000-c000-
000000000046}:'Keywords'] Categories
Error = Element 0 in the multivalue property is invalid...

This issue is documented on the Microsoft Exchange Team Blog at http://msexchangeteam.com/archive/2008/01/10/447843.aspx, and the solution is to simply clear the Category on all of the items using Outlook; the invalid Categories usually display in Outlook as "None" and you will see items arranged in two different "None" Categories. You may have to set them to some other category and then set them back to None to clear the Categories successfully. Once the Categories property is truly clear, you'll only have one set of items that show a Category of "None," and the items will replicate successfully. Now, the above works in theory, but when you're dealing with 200 GB of public folder content finding and correcting the items with invalid Categories through Outlook is simply not feasible. Some automated approaches were taken using scripting, but creating, validating and running these scripts took a considerable amount of time and effort that had to be diverted from the rest of the upgrade project. The lesson learned in this case was that public folders need to be managed on an ongoing basis to avoid having them get out of control, and that you're much better off cleaning up your public folders before attempting to replicate them to the new system.


Other -----------------
- Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 9) - Moving Offline Address Books
- Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 8)
- Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 7) - Coexistence for Management
- Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 6) - Upgrading Message Connectivity From Exchange Server 2003
- Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 5)
- Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 4)
- Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 3)
- Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 2)
- Exchange Server 2010 : Upgrading from and Coexisting with Exchange Server 2003 (part 1)
- Exchange Server 2010 : Useful Tools for an Upgrade (part 1)
- Exchange Server 2010 : Useful Tools for an Upgrade (part 1)
- Active Directory Domain Services 2008: Modify the Precedence for Password Settings Objects
- Active Directory Domain Services 2008: Apply a Password Settings Object to Users and Security Groups
- Active Directory Domain Services 2008: Modify Settings Defined in Password Settings Objects
- BizTalk Server 2009 : Getting results from asynchronous invocations (part 3)
- BizTalk Server 2009 : Getting results from asynchronous invocations (part 2)
- BizTalk Server 2009 : Getting results from asynchronous invocations (part 1) - Building WCF services that support client callbacks
- Exchange Server 2010 : Designing Upgrade and Coexistence Strategies
- Exchange Server 2010 : Risk Mitigation
- Exchange Server 2010 : Planning Cross-site Failovers (part 2) - Cross-site Switchover
 
 
 
Top 10
 
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
- First look: Apple Watch

- 3 Tips for Maintaining Your Cell Phone Battery (part 1)

- 3 Tips for Maintaining Your Cell Phone Battery (part 2)
programming4us programming4us